Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a34a88ee69a8d03ac182d8a2394bd284e5efb963b78f35c755113a94db5d66e

Tx prefix hash: 188c45773e40ef45e0c4262acf2c3fc8af9adbc80d5cdd7ad46f08bf895f8832
Tx public key: cce16678ec6b035d7ca7ee39892c689d3a1d2858cd537f0be4b289d3cb581e21
Timestamp: 1729155359 Timestamp [UCT]: 2024-10-17 08:55:59 Age [y:d:h:m:s]: 00:174:00:32:47
Block: 1133461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124150 RingCT/type: yes/0
Extra: 01cce16678ec6b035d7ca7ee39892c689d3a1d2858cd537f0be4b289d3cb581e2102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa7fbcefa078ad7ba829d5bf0d95ff24ce43ec17638ab26f59fa7cf1ca7584e3 0.600000000000 1616582 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": 1133471, "vin": [ { "gen": { "height": 1133461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa7fbcefa078ad7ba829d5bf0d95ff24ce43ec17638ab26f59fa7cf1ca7584e3" } } ], "extra": [ 1, 204, 225, 102, 120, 236, 107, 3, 93, 124, 167, 238, 57, 137, 44, 104, 157, 58, 29, 40, 88, 205, 83, 127, 11, 228, 178, 137, 211, 203, 88, 30, 33, 2, 17, 0, 0, 0, 7, 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