Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c667462e90737f0a931c3057b7afc70fa2b34bddd5055cc0374aba47d2f074f4

Tx prefix hash: 307fc36ae03bc0c42c5a102d3fb97f6c1bcea4a9266ab121c2bf7d38c9f95fc6
Tx public key: 9f682016e7675970cf80565eabc822c00f7a47df44f696dc56cf957aa1eb3f42
Timestamp: 1722912417 Timestamp [UCT]: 2024-08-06 02:46:57 Age [y:d:h:m:s]: 01:100:00:02:33
Block: 1081696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329965 RingCT/type: yes/0
Extra: 019f682016e7675970cf80565eabc822c00f7a47df44f696dc56cf957aa1eb3f42021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae21d5602b3af78169054ff81d3bb3254c856f73c5234ba2e94d4a2e1d8d22a6 0.600000000000 1555513 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": 1081706, "vin": [ { "gen": { "height": 1081696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae21d5602b3af78169054ff81d3bb3254c856f73c5234ba2e94d4a2e1d8d22a6" } } ], "extra": [ 1, 159, 104, 32, 22, 231, 103, 89, 112, 207, 128, 86, 94, 171, 200, 34, 192, 15, 122, 71, 223, 68, 246, 150, 220, 86, 207, 149, 122, 161, 235, 63, 66, 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