Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54dc8806821d4ca862a6a7d77f9c1c6a3776432f3103897abf4c1d40f395d18e

Tx prefix hash: 1943afef76cbd4801b7d41005fde78142cbcf9fdb5a9b4380e5bb76b78658ed4
Tx public key: db066b5bd11af7615579b55bb4b0d0f8f01341dec44671baa5e2f3be9e54cc7b
Timestamp: 1577833816 Timestamp [UCT]: 2019-12-31 23:10:16 Age [y:d:h:m:s]: 05:002:16:39:19
Block: 36048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151920 RingCT/type: yes/0
Extra: 01db066b5bd11af7615579b55bb4b0d0f8f01341dec44671baa5e2f3be9e54cc7b02110000003b398c17aa000000000000000000

1 output(s) for total of 466.185611498000 dcy

stealth address amount amount idx
00: b401e0f2eaa66429770390d0146762d98696ec0d767fbd01ad50917226337772 466.185611498000 60920 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": 36058, "vin": [ { "gen": { "height": 36048 } } ], "vout": [ { "amount": 466185611498, "target": { "key": "b401e0f2eaa66429770390d0146762d98696ec0d767fbd01ad50917226337772" } } ], "extra": [ 1, 219, 6, 107, 91, 209, 26, 247, 97, 85, 121, 181, 91, 180, 176, 208, 248, 240, 19, 65, 222, 196, 70, 113, 186, 165, 226, 243, 190, 158, 84, 204, 123, 2, 17, 0, 0, 0, 59, 57, 140, 23, 170, 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