Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e40a156804093948c871f5446d5f47fd56de9ed29e2fb242202e005c5d67e32

Tx prefix hash: 3a3cbdcf3c9a1b500444038e818ecc6c162b89867d28a4729ee2442641bbddb1
Tx public key: 6607226a930ac6d754b1c0885946895f04f924b1aae539df6975cac54aadc5bc
Timestamp: 1671388783 Timestamp [UCT]: 2022-12-18 18:39:43 Age [y:d:h:m:s]: 02:145:19:13:36
Block: 655433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 625917 RingCT/type: yes/0
Extra: 016607226a930ac6d754b1c0885946895f04f924b1aae539df6975cac54aadc5bc0211000000025029cbac000000000000000000

1 output(s) for total of 4.133123347000 dcy

stealth address amount amount idx
00: ccc9d02b7869437dc31c739e1e2d63f3ee6928a602939fb0e0e14b143329f218 4.133123347000 1095990 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": 655443, "vin": [ { "gen": { "height": 655433 } } ], "vout": [ { "amount": 4133123347, "target": { "key": "ccc9d02b7869437dc31c739e1e2d63f3ee6928a602939fb0e0e14b143329f218" } } ], "extra": [ 1, 102, 7, 34, 106, 147, 10, 198, 215, 84, 177, 192, 136, 89, 70, 137, 95, 4, 249, 36, 177, 170, 229, 57, 223, 105, 117, 202, 197, 74, 173, 197, 188, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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