Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0596335a4aa9031a8293a3ac8339c6623688d9d4925750dc27d44cddbf5ebfc2

Tx prefix hash: b1260176f6cdeb271ab70a6888f7d238138a8d41673bdbc91a3f7705fc637fd0
Tx public key: 73c0c9b40416ec168e1a6b98aa17cc3f47708211ddf6f825c840b788a6d03662
Timestamp: 1735688776 Timestamp [UCT]: 2024-12-31 23:46:16 Age [y:d:h:m:s]: 00:087:09:44:47
Block: 1187490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62254 RingCT/type: yes/0
Extra: 0173c0c9b40416ec168e1a6b98aa17cc3f47708211ddf6f825c840b788a6d036620211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8eb42775b8ff29db15d7cf5249fe4d1a5885881a8c7dd321ec4eacd08a3e178c 0.600000000000 1673981 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": 1187500, "vin": [ { "gen": { "height": 1187490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8eb42775b8ff29db15d7cf5249fe4d1a5885881a8c7dd321ec4eacd08a3e178c" } } ], "extra": [ 1, 115, 192, 201, 180, 4, 22, 236, 22, 142, 26, 107, 152, 170, 23, 204, 63, 71, 112, 130, 17, 221, 246, 248, 37, 200, 64, 183, 136, 166, 208, 54, 98, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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