Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d207578268cb64685f5744546d44edb942caf4417123e431a5a9e962c876e33b

Tx prefix hash: 4c1a89b5a61683e9d3bb84892dcabaf71a576641c64b6f6003762053fb22bf20
Tx public key: 12bcde32b7c889bc306c3f8644567555e3eedb85e3cf2931a5e5b815e43ba45b
Timestamp: 1723866580 Timestamp [UCT]: 2024-08-17 03:49:40 Age [y:d:h:m:s]: 00:227:23:26:15
Block: 1089619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162787 RingCT/type: yes/0
Extra: 0112bcde32b7c889bc306c3f8644567555e3eedb85e3cf2931a5e5b815e43ba45b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6f3051e0a561cb96a6853eaf9a5df0302ce12dce24d71cb6cde23a5f47c2906 0.600000000000 1564242 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": 1089629, "vin": [ { "gen": { "height": 1089619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6f3051e0a561cb96a6853eaf9a5df0302ce12dce24d71cb6cde23a5f47c2906" } } ], "extra": [ 1, 18, 188, 222, 50, 183, 200, 137, 188, 48, 108, 63, 134, 68, 86, 117, 85, 227, 238, 219, 133, 227, 207, 41, 49, 165, 229, 184, 21, 228, 59, 164, 91, 2, 17, 0, 0, 0, 1, 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