Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56caf6c319cbe0a12018c4e2aa5e35050972316ac8b4629fa1ef057ef419d13d

Tx prefix hash: 09944001ac45f42576d3bacc22ff256703728fd931c1bc603b4ad228e7200bcc
Tx public key: be3ac797acb1b61e638360851af8b661c84f5afc1dab96c292f17778f961a6ee
Timestamp: 1706541246 Timestamp [UCT]: 2024-01-29 15:14:06 Age [y:d:h:m:s]: 01:285:04:26:47
Block: 945953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462630 RingCT/type: yes/0
Extra: 01be3ac797acb1b61e638360851af8b661c84f5afc1dab96c292f17778f961a6ee02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69e1cf5eaaac07a79a045c59866fd5f84b4a31a8bf63a5233d239c8460224186 0.600000000000 1404283 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": 945963, "vin": [ { "gen": { "height": 945953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69e1cf5eaaac07a79a045c59866fd5f84b4a31a8bf63a5233d239c8460224186" } } ], "extra": [ 1, 190, 58, 199, 151, 172, 177, 182, 30, 99, 131, 96, 133, 26, 248, 182, 97, 200, 79, 90, 252, 29, 171, 150, 194, 146, 241, 119, 120, 249, 97, 166, 238, 2, 17, 0, 0, 0, 6, 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