Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f636aa1c2592d9cd56ef4d6c09351590b0416673e543f7a129a189e232b84792

Tx prefix hash: 8eacf8b2f60ae9cfe8a0474761637f2c0a6a2cd6322329a1b7585accce3f7273
Tx public key: ff54965c5136b833ba1dcec9abf47528a2faf6b3d41ccfe5ed94691fd063f7ae
Timestamp: 1763577102 Timestamp [UCT]: 2025-11-19 18:31:42 Age [y:d:h:m:s]: 00:006:19:45:31
Block: 1415703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4885 RingCT/type: yes/0
Extra: 01ff54965c5136b833ba1dcec9abf47528a2faf6b3d41ccfe5ed94691fd063f7ae02110000000c70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 553214e863cadeb158ffdb7d5537c60ca62a72040fbe9f62b3cb23dcf0f6ae2a 0.600000000000 1904208 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": 1415713, "vin": [ { "gen": { "height": 1415703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553214e863cadeb158ffdb7d5537c60ca62a72040fbe9f62b3cb23dcf0f6ae2a" } } ], "extra": [ 1, 255, 84, 150, 92, 81, 54, 184, 51, 186, 29, 206, 201, 171, 244, 117, 40, 162, 250, 246, 179, 212, 28, 207, 229, 237, 148, 105, 31, 208, 99, 247, 174, 2, 17, 0, 0, 0, 12, 112, 96, 157, 3, 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