Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c86c395b6b814bbdeaa26915761cf4e60074811c35c8054d9bf3f1da698a5f

Tx prefix hash: f153b4f79890329b6c59556e2476833d97f5b74c78cd2f478a605e852925f606
Tx public key: 7afdce735419c8c7200d3ed9054dbb821e8a8e4fcef54a1e8c3b40314733d1ed
Timestamp: 1723844286 Timestamp [UCT]: 2024-08-16 21:38:06 Age [y:d:h:m:s]: 00:100:05:10:03
Block: 1089428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71686 RingCT/type: yes/0
Extra: 017afdce735419c8c7200d3ed9054dbb821e8a8e4fcef54a1e8c3b40314733d1ed02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5bf4fdeb689026183a2b51b8eaecb8561ef5db635d66dbeb760999b063d5614 0.600000000000 1564049 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": 1089438, "vin": [ { "gen": { "height": 1089428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5bf4fdeb689026183a2b51b8eaecb8561ef5db635d66dbeb760999b063d5614" } } ], "extra": [ 1, 122, 253, 206, 115, 84, 25, 200, 199, 32, 13, 62, 217, 5, 77, 187, 130, 30, 138, 142, 79, 206, 245, 74, 30, 140, 59, 64, 49, 71, 51, 209, 237, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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