Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39be88c7ae23f42c9ce79bc55292589c9dc1739f3550ca5434dd431ded3d07cf

Tx prefix hash: ba3dd78d68fd37c7ec9121cdb136fcfc11591bb2987736519cc2aa5b282a0f0a
Tx public key: 2e31901348add3c974a8097f61d8c80853b6c926e8b793f8675408f59e444c6d
Timestamp: 1711219506 Timestamp [UCT]: 2024-03-23 18:45:06 Age [y:d:h:m:s]: 01:085:23:30:36
Block: 984783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322330 RingCT/type: yes/0
Extra: 012e31901348add3c974a8097f61d8c80853b6c926e8b793f8675408f59e444c6d02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc8f59d23139bb840a564d3c48d7580ffc196f396aee3490c7874f804c6792b2 0.600000000000 1444956 of 15

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": 984793, "vin": [ { "gen": { "height": 984783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc8f59d23139bb840a564d3c48d7580ffc196f396aee3490c7874f804c6792b2" } } ], "extra": [ 1, 46, 49, 144, 19, 72, 173, 211, 201, 116, 168, 9, 127, 97, 216, 200, 8, 83, 182, 201, 38, 232, 183, 147, 248, 103, 84, 8, 245, 158, 68, 76, 109, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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