Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395dc507f47eec412b6a94b7af2603f107e22fe7fd8691cacc22885be7cece91

Tx prefix hash: 8d0c6bfbb5b10b51ced6f6be11dd469458cb66c6fa16f99ce9b95a6c2fd3a343
Tx public key: 80356ef81af5e64b658e25ec24dd127f9bf537d3184beb1c664c8e209d3505ad
Timestamp: 1577485564 Timestamp [UCT]: 2019-12-27 22:26:04 Age [y:d:h:m:s]: 04:335:12:53:43
Block: 33112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128973 RingCT/type: yes/0
Extra: 0180356ef81af5e64b658e25ec24dd127f9bf537d3184beb1c664c8e209d3505ad021100000080c5b5978f000000000000000000

1 output(s) for total of 476.745998210000 dcy

stealth address amount amount idx
00: c16c240f5f1b7823a566c9beefe09e38add57adefa6580adcb19b573ca60a8d6 476.745998210000 55298 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": 33122, "vin": [ { "gen": { "height": 33112 } } ], "vout": [ { "amount": 476745998210, "target": { "key": "c16c240f5f1b7823a566c9beefe09e38add57adefa6580adcb19b573ca60a8d6" } } ], "extra": [ 1, 128, 53, 110, 248, 26, 245, 230, 75, 101, 142, 37, 236, 36, 221, 18, 127, 155, 245, 55, 211, 24, 75, 235, 28, 102, 76, 142, 32, 157, 53, 5, 173, 2, 17, 0, 0, 0, 128, 197, 181, 151, 143, 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