Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee44b3eebbaf53ad45d32e359c1fb5e1795f8f8e9be5511fbd42cea8486f6cbd

Tx prefix hash: d2c7de2abc85608def8b4056b7f119416682b8c14ea60ac2d6d7cfc521e20eed
Tx public key: fca9f6dd5fff36c32e355b3935a343cbd2de2bcc6a045b9aec26799ee89785a9
Timestamp: 1764959349 Timestamp [UCT]: 2025-12-05 18:29:09 Age [y:d:h:m:s]: 00:011:00:11:09
Block: 1427147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7882 RingCT/type: yes/0
Extra: 01fca9f6dd5fff36c32e355b3935a343cbd2de2bcc6a045b9aec26799ee89785a902110000000970609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1901a063b577c4ca28818e1ae2d03b0915b3d300af654f36073d50388674e93 0.600000000000 1915846 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": 1427157, "vin": [ { "gen": { "height": 1427147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1901a063b577c4ca28818e1ae2d03b0915b3d300af654f36073d50388674e93" } } ], "extra": [ 1, 252, 169, 246, 221, 95, 255, 54, 195, 46, 53, 91, 57, 53, 163, 67, 203, 210, 222, 43, 204, 106, 4, 91, 154, 236, 38, 121, 158, 232, 151, 133, 169, 2, 17, 0, 0, 0, 9, 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