Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59d3efda54c3ebe7e9756dd1970adb805f1cb931e92ecf6cbd543d3f201a087b

Tx prefix hash: 915051bdf4215e256fc007c1d9fe7df7565d81973838926f9daaf3a37285d714
Tx public key: b603575aa78c53ed544ca882c72c7a6f6f466de57cff326f12e885e568a07745
Timestamp: 1634824088 Timestamp [UCT]: 2021-10-21 13:48:08 Age [y:d:h:m:s]: 03:037:12:54:10
Block: 357489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 805046 RingCT/type: yes/0
Extra: 01b603575aa78c53ed544ca882c72c7a6f6f466de57cff326f12e885e568a0774502110000001afdc024ec000000000000000000

1 output(s) for total of 40.132013981000 dcy

stealth address amount amount idx
00: 86ce0fd84671077cc6fd3fdbc5b122d810b78b0d5d0514943746cb319e4bb0e8 40.132013981000 728935 of 0

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": 357499, "vin": [ { "gen": { "height": 357489 } } ], "vout": [ { "amount": 40132013981, "target": { "key": "86ce0fd84671077cc6fd3fdbc5b122d810b78b0d5d0514943746cb319e4bb0e8" } } ], "extra": [ 1, 182, 3, 87, 90, 167, 140, 83, 237, 84, 76, 168, 130, 199, 44, 122, 111, 111, 70, 109, 229, 124, 255, 50, 111, 18, 232, 133, 229, 104, 160, 119, 69, 2, 17, 0, 0, 0, 26, 253, 192, 36, 236, 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