Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f5cb1609accc8e31df53aed2fdb4a4c1a7347a7b985ea8c7f6c9838682b1e1

Tx prefix hash: bb201fabe720acc870deb13ed85efc09722419b552ccd96dd3fe9c2bc5993feb
Tx public key: d7d0e93801beb2b01f69d528631ca4e3205c666509994b0a7d6d696d9accbf1f
Timestamp: 1646521559 Timestamp [UCT]: 2022-03-05 23:05:59 Age [y:d:h:m:s]: 02:257:21:39:58
Block: 452141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703791 RingCT/type: yes/0
Extra: 01d7d0e93801beb2b01f69d528631ca4e3205c666509994b0a7d6d696d9accbf1f021100000019cb8520c2000000000000000000

1 output(s) for total of 19.495325596000 dcy

stealth address amount amount idx
00: 0033ae4363b7ec2d2022da409deafab8861b6ce5853fb37e5dc8c84c3f31abb7 19.495325596000 867388 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": 452151, "vin": [ { "gen": { "height": 452141 } } ], "vout": [ { "amount": 19495325596, "target": { "key": "0033ae4363b7ec2d2022da409deafab8861b6ce5853fb37e5dc8c84c3f31abb7" } } ], "extra": [ 1, 215, 208, 233, 56, 1, 190, 178, 176, 31, 105, 213, 40, 99, 28, 164, 227, 32, 92, 102, 101, 9, 153, 75, 10, 125, 109, 105, 109, 154, 204, 191, 31, 2, 17, 0, 0, 0, 25, 203, 133, 32, 194, 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