Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45d4b05bf859fd8600c947c6aea36311cb53dc89c40a3bc3bfb671ada464ac22

Tx prefix hash: 8493d3c64f55147c475a2f20e39c5b0676d936ada56335c0ea7fec73bda64545
Tx public key: 4e956cb84a0b3f17aae681f8d1ef15321ba71108be7d6550c749fc710560563c
Timestamp: 1736683627 Timestamp [UCT]: 2025-01-12 12:07:07 Age [y:d:h:m:s]: 00:070:09:57:24
Block: 1195729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50092 RingCT/type: yes/0
Extra: 014e956cb84a0b3f17aae681f8d1ef15321ba71108be7d6550c749fc710560563c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24cf1edf7377c16274ef9c18dc957e6389a2c637f676a1d2d7738f1dc233d91e 0.600000000000 1682322 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": 1195739, "vin": [ { "gen": { "height": 1195729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24cf1edf7377c16274ef9c18dc957e6389a2c637f676a1d2d7738f1dc233d91e" } } ], "extra": [ 1, 78, 149, 108, 184, 74, 11, 63, 23, 170, 230, 129, 248, 209, 239, 21, 50, 27, 167, 17, 8, 190, 125, 101, 80, 199, 73, 252, 113, 5, 96, 86, 60, 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