Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5981802e934108530ef313c050f93a2550f99db913cd00a120112be3519c2854

Tx prefix hash: 8e49643f368b5c176376ae335c6d636011a38e1153ac4c79a2133b38e3189e71
Tx public key: 1aa64b461e8c251c0dee1d78800a8256d6b746921f981ce46a0b4f1fd9e460df
Timestamp: 1749457781 Timestamp [UCT]: 2025-06-09 08:29:41 Age [y:d:h:m:s]: 00:158:16:27:02
Block: 1301222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111095 RingCT/type: yes/0
Extra: 011aa64b461e8c251c0dee1d78800a8256d6b746921f981ce46a0b4f1fd9e460df02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c67ea2df8081f58b3723e5a32539513c6f526d6733d00947d265293601f0a969 0.600000000000 1788779 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": 1301232, "vin": [ { "gen": { "height": 1301222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c67ea2df8081f58b3723e5a32539513c6f526d6733d00947d265293601f0a969" } } ], "extra": [ 1, 26, 166, 75, 70, 30, 140, 37, 28, 13, 238, 29, 120, 128, 10, 130, 86, 214, 183, 70, 146, 31, 152, 28, 228, 106, 11, 79, 31, 217, 228, 96, 223, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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