Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4395933c30a5beaf1b9181fc0df3688ca315b6b7724f3a956608ff498e850594

Tx prefix hash: d8586565edc76414c9f237ddb1fc7b6d120ba54b41cdfcbd8925ae5ec863e168
Tx public key: 8e3834b1b8a9e083a8a6eff8090395e0acce75789b8a1a34ec4fecc16a003ae3
Timestamp: 1728584524 Timestamp [UCT]: 2024-10-10 18:22:04 Age [y:d:h:m:s]: 00:254:20:58:30
Block: 1128722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181811 RingCT/type: yes/0
Extra: 018e3834b1b8a9e083a8a6eff8090395e0acce75789b8a1a34ec4fecc16a003ae302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1266034e86f015407593babe6f72288bafae3f1e742c5b525b2ae699e141f5 0.600000000000 1611543 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": 1128732, "vin": [ { "gen": { "height": 1128722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1266034e86f015407593babe6f72288bafae3f1e742c5b525b2ae699e141f5" } } ], "extra": [ 1, 142, 56, 52, 177, 184, 169, 224, 131, 168, 166, 239, 248, 9, 3, 149, 224, 172, 206, 117, 120, 155, 138, 26, 52, 236, 79, 236, 193, 106, 0, 58, 227, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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