Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1b52e0adc912b96efbae58faf94457d78b365c40e5d03e100b8922d2fd9ea70

Tx prefix hash: 5ee684ec3abc98d2844b88c1df435d5f8cc858df06bae28cc7882b832d030abd
Tx public key: cb98e8036ade39b59a44510580044040d34bb1951c9e504df4d2382fa503e87e
Timestamp: 1702763248 Timestamp [UCT]: 2023-12-16 21:47:28 Age [y:d:h:m:s]: 01:034:16:15:21
Block: 914653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286098 RingCT/type: yes/0
Extra: 01cb98e8036ade39b59a44510580044040d34bb1951c9e504df4d2382fa503e87e02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed00456dc4c1fd040d296a7699c88a9975a4a6fe5762c9eaaef0fdfa417331f3 0.600000000000 1372003 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": 914663, "vin": [ { "gen": { "height": 914653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed00456dc4c1fd040d296a7699c88a9975a4a6fe5762c9eaaef0fdfa417331f3" } } ], "extra": [ 1, 203, 152, 232, 3, 106, 222, 57, 181, 154, 68, 81, 5, 128, 4, 64, 64, 211, 75, 177, 149, 28, 158, 80, 77, 244, 210, 56, 47, 165, 3, 232, 126, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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