Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7acdc34a982896216d275766dcba0ebe2ec119306d91895fd062c855735f05

Tx prefix hash: 16a072a9b662f487cdb8720358126063f02191e9e3f426a6f78514381db9f3f4
Tx public key: e31665a7ce23a572bfcff86780e1d3de62e928b4e66d9819a537622003c519c6
Timestamp: 1701845009 Timestamp [UCT]: 2023-12-06 06:43:29 Age [y:d:h:m:s]: 01:199:13:28:35
Block: 907040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403609 RingCT/type: yes/0
Extra: 01e31665a7ce23a572bfcff86780e1d3de62e928b4e66d9819a537622003c519c602110000000479bda3be000000000000000000

1 output(s) for total of 0.606177654000 dcy

stealth address amount amount idx
00: 8702234c5fa3e9ffe198b8ce68d6a4ed49ea24ffd4b3ea4ce66dbb7eea5da011 0.606177654000 1364003 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": 907050, "vin": [ { "gen": { "height": 907040 } } ], "vout": [ { "amount": 606177654, "target": { "key": "8702234c5fa3e9ffe198b8ce68d6a4ed49ea24ffd4b3ea4ce66dbb7eea5da011" } } ], "extra": [ 1, 227, 22, 101, 167, 206, 35, 165, 114, 191, 207, 248, 103, 128, 225, 211, 222, 98, 233, 40, 180, 230, 109, 152, 25, 165, 55, 98, 32, 3, 197, 25, 198, 2, 17, 0, 0, 0, 4, 121, 189, 163, 190, 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