Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e63e8303ef02203810341a563b7e1b3c8af2cb278ae00700465000dcacb5714

Tx prefix hash: 6015c73e47d888f509f75df7ad2cb3cddbd6959a0b166a2191c16fc7ffd553b4
Tx public key: 64e95d65144faf4387a4bcf8c23379b89a8907b09fe734a446e1586d93000121
Timestamp: 1694417485 Timestamp [UCT]: 2023-09-11 07:31:25 Age [y:d:h:m:s]: 01:066:21:04:51
Block: 845643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309093 RingCT/type: yes/0
Extra: 0164e95d65144faf4387a4bcf8c23379b89a8907b09fe734a446e1586d9300012102110000000133af99f4000000000000000000

1 output(s) for total of 0.968353131000 dcy

stealth address amount amount idx
00: 5356b103513f52fcb41da7e5f0a85dce4c1dc48f17bc3dba5e1e38bdba4dc5e6 0.968353131000 1299051 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": 845653, "vin": [ { "gen": { "height": 845643 } } ], "vout": [ { "amount": 968353131, "target": { "key": "5356b103513f52fcb41da7e5f0a85dce4c1dc48f17bc3dba5e1e38bdba4dc5e6" } } ], "extra": [ 1, 100, 233, 93, 101, 20, 79, 175, 67, 135, 164, 188, 248, 194, 51, 121, 184, 154, 137, 7, 176, 159, 231, 52, 164, 70, 225, 88, 109, 147, 0, 1, 33, 2, 17, 0, 0, 0, 1, 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