Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fea8e0efbc63a241a1114403e3c530802daf2aa8af67ad7ca6dd0fdedd6aeb7f

Tx prefix hash: e88729506ded2771015b8085dd350671481562c316c33b57ace2e181b60d32a1
Tx public key: 749fc7b73f0160beba1aa8260f7e76e6d1d1cef98e9c9b54914550a7d94f37e4
Timestamp: 1736025698 Timestamp [UCT]: 2025-01-04 21:21:38 Age [y:d:h:m:s]: 00:071:15:27:52
Block: 1190286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50997 RingCT/type: yes/0
Extra: 01749fc7b73f0160beba1aa8260f7e76e6d1d1cef98e9c9b54914550a7d94f37e4021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b0af374a8bf3155a8a0172508492532fa90d75374f1d28b09b71af558643df0 0.600000000000 1676801 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": 1190296, "vin": [ { "gen": { "height": 1190286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b0af374a8bf3155a8a0172508492532fa90d75374f1d28b09b71af558643df0" } } ], "extra": [ 1, 116, 159, 199, 183, 63, 1, 96, 190, 186, 26, 168, 38, 15, 126, 118, 230, 209, 209, 206, 249, 142, 156, 155, 84, 145, 69, 80, 167, 217, 79, 55, 228, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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