Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c646f0668c50f3a07e5013d3810c65ad83b4ad0628e31b2b780eed7cd302ab8

Tx prefix hash: aa796d7fc1bee6de924eb5abf8fd2c51e8bc69fa897ec5fa17d86ff58f902369
Tx public key: de5a25a35f5778d5f455ab5eab8deaf3e9a97600bbaa3328156c993f622515ca
Timestamp: 1736818253 Timestamp [UCT]: 2025-01-14 01:30:53 Age [y:d:h:m:s]: 00:157:03:01:20
Block: 1196843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111983 RingCT/type: yes/0
Extra: 01de5a25a35f5778d5f455ab5eab8deaf3e9a97600bbaa3328156c993f622515ca0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e1dfccdeba42cec69a1aca5ed8bd202f5c8b438980e27153e9864dcfb50efe9 0.600000000000 1683446 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": 1196853, "vin": [ { "gen": { "height": 1196843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e1dfccdeba42cec69a1aca5ed8bd202f5c8b438980e27153e9864dcfb50efe9" } } ], "extra": [ 1, 222, 90, 37, 163, 95, 87, 120, 213, 244, 85, 171, 94, 171, 141, 234, 243, 233, 169, 118, 0, 187, 170, 51, 40, 21, 108, 153, 63, 98, 37, 21, 202, 2, 17, 0, 0, 0, 2, 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