Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42623237325c5de6657d1da20d5c01bcaca524cc9dfc3b6829bcba046848030f

Tx prefix hash: e8595f5c8b74a850a4f4a54511a084c9c5653ff71227b09902453e91580e223f
Tx public key: 865c294abc2f6bfcd8ace4b59072ea8051b79962e53b9b32725907dd0e8aec0f
Timestamp: 1727479097 Timestamp [UCT]: 2024-09-27 23:18:17 Age [y:d:h:m:s]: 00:199:18:13:19
Block: 1119554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142587 RingCT/type: yes/0
Extra: 01865c294abc2f6bfcd8ace4b59072ea8051b79962e53b9b32725907dd0e8aec0f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51ef289df02e4af996e07b5b5733dfe37cc1c3ec57e05479d146ec7b769aaefc 0.600000000000 1601153 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": 1119564, "vin": [ { "gen": { "height": 1119554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51ef289df02e4af996e07b5b5733dfe37cc1c3ec57e05479d146ec7b769aaefc" } } ], "extra": [ 1, 134, 92, 41, 74, 188, 47, 107, 252, 216, 172, 228, 181, 144, 114, 234, 128, 81, 183, 153, 98, 229, 59, 155, 50, 114, 89, 7, 221, 14, 138, 236, 15, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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