Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac52d354cf8b2ed16717263fdbd30b4ce15a0dfcdadf539ecacbe3a5a59a7f8

Tx prefix hash: a344a4994f566845211eb210e6cf0d19709774387806d667e2a9889d37769aca
Tx public key: 3ad11fbc8c0154bf2cc5732afc4a0973a4dd9cf536cf7be2aa2599ac1b75ea50
Timestamp: 1711554289 Timestamp [UCT]: 2024-03-27 15:44:49 Age [y:d:h:m:s]: 00:293:11:14:58
Block: 987564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210039 RingCT/type: yes/0
Extra: 013ad11fbc8c0154bf2cc5732afc4a0973a4dd9cf536cf7be2aa2599ac1b75ea5002110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6bffb020ab910fc1acad909d2c9c5a6eab3df0b7cdad407d92f311ea4795a0e 0.600000000000 1447817 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": 987574, "vin": [ { "gen": { "height": 987564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6bffb020ab910fc1acad909d2c9c5a6eab3df0b7cdad407d92f311ea4795a0e" } } ], "extra": [ 1, 58, 209, 31, 188, 140, 1, 84, 191, 44, 197, 115, 42, 252, 74, 9, 115, 164, 221, 156, 245, 54, 207, 123, 226, 170, 37, 153, 172, 27, 117, 234, 80, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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