Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031610ed33e4b6e524e0d5f9654cec08b6abad7fe22173c9a09be3841fb8ce12

Tx prefix hash: e0c73ccbbbbf2fd4acd329fa2f469ec17a03f2a216e83bf8afa0fc84623b26c1
Tx public key: 6a387b654aa5d43e6adc67e0e67e7d33405946ff8e17fcf89aaf8c03c4eede24
Timestamp: 1577294117 Timestamp [UCT]: 2019-12-25 17:15:17 Age [y:d:h:m:s]: 05:357:18:26:46
Block: 31568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1403264 RingCT/type: yes/0
Extra: 016a387b654aa5d43e6adc67e0e67e7d33405946ff8e17fcf89aaf8c03c4eede240211000000014943cd9f000000000000000000

1 output(s) for total of 482.395193019000 dcy

stealth address amount amount idx
00: 4d2f8d17a267990a9e802d807c3fef133eaa5f8692e291fce892a7eda7585ed3 482.395193019000 52253 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": 31578, "vin": [ { "gen": { "height": 31568 } } ], "vout": [ { "amount": 482395193019, "target": { "key": "4d2f8d17a267990a9e802d807c3fef133eaa5f8692e291fce892a7eda7585ed3" } } ], "extra": [ 1, 106, 56, 123, 101, 74, 165, 212, 62, 106, 220, 103, 224, 230, 126, 125, 51, 64, 89, 70, 255, 142, 23, 252, 248, 154, 175, 140, 3, 196, 238, 222, 36, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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