Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e36c880fbff9c7d6b1b317ed1267159ccf0a36ee70a22ee7a215f98492406950

Tx prefix hash: 066ef9bcb25eef9df18d8a52245ebc3e8672b00291c2e7fdda58d286990b719d
Tx public key: ab4492644ea32195c8c9721ef83b163b8e4907f7637abf0a6eec20d77cab95e3
Timestamp: 1705619545 Timestamp [UCT]: 2024-01-18 23:12:25 Age [y:d:h:m:s]: 01:306:03:02:59
Block: 938313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477624 RingCT/type: yes/0
Extra: 01ab4492644ea32195c8c9721ef83b163b8e4907f7637abf0a6eec20d77cab95e30211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2694ed01dfe37f8e17df413c6b16a035b5ed4a283ba00ac6f95d6a662dda6d0 0.600000000000 1396383 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": 938323, "vin": [ { "gen": { "height": 938313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2694ed01dfe37f8e17df413c6b16a035b5ed4a283ba00ac6f95d6a662dda6d0" } } ], "extra": [ 1, 171, 68, 146, 100, 78, 163, 33, 149, 200, 201, 114, 30, 248, 59, 22, 59, 142, 73, 7, 247, 99, 122, 191, 10, 110, 236, 32, 215, 124, 171, 149, 227, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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