Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5226ec772a0ecefad2d037b7959d47fe97d049ccceb7b08e75d0c80cdfc3be96

Tx prefix hash: e8029a9e9f280f2b163fcc66f939e5206e4fae9bfc76ed23317e1edbfd57f313
Tx public key: 4a5bb5f562e373fa564b2cf69a6aa8ea7cc629ee209c4ce87f9d428eecbad8dd
Timestamp: 1766068497 Timestamp [UCT]: 2025-12-18 14:34:57 Age [y:d:h:m:s]: 00:004:10:20:49
Block: 1436350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3166 RingCT/type: yes/0
Extra: 014a5bb5f562e373fa564b2cf69a6aa8ea7cc629ee209c4ce87f9d428eecbad8dd0211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a04545a84049cb3c289d63b85ce93b589cf0555607f84a34660079daf291247f 0.600000000000 1925155 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": 1436360, "vin": [ { "gen": { "height": 1436350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a04545a84049cb3c289d63b85ce93b589cf0555607f84a34660079daf291247f" } } ], "extra": [ 1, 74, 91, 181, 245, 98, 227, 115, 250, 86, 75, 44, 246, 154, 106, 168, 234, 124, 198, 41, 238, 32, 156, 76, 232, 127, 157, 66, 142, 236, 186, 216, 221, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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