Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08922a981a144842c539ff76af8be3710085ad9cfca98f043df8f04c09b9e57d

Tx prefix hash: 0e8c2fb7e78c8f7e2e40a74e6013196c84f493f4667ff11effe81ff309110a80
Tx public key: 6c4dc95cac4d5d3d2751c510b7f40eebc01a3dd5bf650bbf22dac70d708237cf
Timestamp: 1589363813 Timestamp [UCT]: 2020-05-13 09:56:53 Age [y:d:h:m:s]: 04:295:19:15:25
Block: 100509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131218 RingCT/type: yes/0
Extra: 016c4dc95cac4d5d3d2751c510b7f40eebc01a3dd5bf650bbf22dac70d708237cf02110000019f86362411000000000000000000

1 output(s) for total of 285.106319362000 dcy

stealth address amount amount idx
00: 8f5424bf8e92fa110d8c1d55bfb6d02b6ca8d9c6c195c96b7ebac0d0bf41a658 285.106319362000 177057 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": 100519, "vin": [ { "gen": { "height": 100509 } } ], "vout": [ { "amount": 285106319362, "target": { "key": "8f5424bf8e92fa110d8c1d55bfb6d02b6ca8d9c6c195c96b7ebac0d0bf41a658" } } ], "extra": [ 1, 108, 77, 201, 92, 172, 77, 93, 61, 39, 81, 197, 16, 183, 244, 14, 235, 192, 26, 61, 213, 191, 101, 11, 191, 34, 218, 199, 13, 112, 130, 55, 207, 2, 17, 0, 0, 1, 159, 134, 54, 36, 17, 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