Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee69d5bd2de8ba93e24e3e20f697f7cda081e02e0c92abdba1904cc7d9f996ab

Tx prefix hash: 0f718fa7a4982d943fc26482ce1d5e841d85db062e4b62daba4036471a452b19
Tx public key: bfd983605ba7ac1594f810577917cdc1641b2a31bed4cb2af7ac2dd2e7c23c0d
Timestamp: 1705282914 Timestamp [UCT]: 2024-01-15 01:41:54 Age [y:d:h:m:s]: 01:093:20:15:36
Block: 935514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328180 RingCT/type: yes/0
Extra: 01bfd983605ba7ac1594f810577917cdc1641b2a31bed4cb2af7ac2dd2e7c23c0d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c17f84908f4af3c265de39fd3483b8e5e72822de70aaea57030f5e268398d8b0 0.600000000000 1393530 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": 935524, "vin": [ { "gen": { "height": 935514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c17f84908f4af3c265de39fd3483b8e5e72822de70aaea57030f5e268398d8b0" } } ], "extra": [ 1, 191, 217, 131, 96, 91, 167, 172, 21, 148, 248, 16, 87, 121, 23, 205, 193, 100, 27, 42, 49, 190, 212, 203, 42, 247, 172, 45, 210, 231, 194, 60, 13, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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