Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c75f1650362bf6e105524cfb01c7113bf40391e96b158a6fad3a066c13e609

Tx prefix hash: a34574901fb0ccbfb97ef34f3146a304dec7916506e6b6a265b0690f69f8c69a
Tx public key: dba63ce271d7385b3e430c4730faead92b5f0d1ee7ec0424bb07f3d1d7165a7d
Timestamp: 1737047225 Timestamp [UCT]: 2025-01-16 17:07:05 Age [y:d:h:m:s]: 00:153:17:15:30
Block: 1198739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109551 RingCT/type: yes/0
Extra: 01dba63ce271d7385b3e430c4730faead92b5f0d1ee7ec0424bb07f3d1d7165a7d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7b9a6fbb502ae46a3189cd17c879ad09a3797d3c7956fb691f2e86e46537d13 0.600000000000 1685366 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": 1198749, "vin": [ { "gen": { "height": 1198739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7b9a6fbb502ae46a3189cd17c879ad09a3797d3c7956fb691f2e86e46537d13" } } ], "extra": [ 1, 219, 166, 60, 226, 113, 215, 56, 91, 62, 67, 12, 71, 48, 250, 234, 217, 43, 95, 13, 30, 231, 236, 4, 36, 187, 7, 243, 209, 215, 22, 90, 125, 2, 17, 0, 0, 0, 1, 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