Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6161cb0f2dfd774b9f4680b9717dc8aba2d7f2bab198c21747012e837ff634f9

Tx prefix hash: bcac17263f79a27d828bf06e0b5ca6c05dd6b1692fae65e83925434d0704b24e
Tx public key: 7df4cf3abd0f4dddc634fa674f39dae9207f80301de0c31353c5c6a0b3f54870
Timestamp: 1723372533 Timestamp [UCT]: 2024-08-11 10:35:33 Age [y:d:h:m:s]: 00:248:02:43:58
Block: 1085518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177217 RingCT/type: yes/0
Extra: 017df4cf3abd0f4dddc634fa674f39dae9207f80301de0c31353c5c6a0b3f5487002110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2318e61cc6edc83625217164b9e30265e2cabb50c3a2514537f78885258ceff6 0.600000000000 1560105 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1085528, "vin": [ { "gen": { "height": 1085518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2318e61cc6edc83625217164b9e30265e2cabb50c3a2514537f78885258ceff6" } } ], "extra": [ 1, 125, 244, 207, 58, 189, 15, 77, 221, 198, 52, 250, 103, 79, 57, 218, 233, 32, 127, 128, 48, 29, 224, 195, 19, 83, 197, 198, 160, 179, 245, 72, 112, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8