Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4592ef95946643776b4d0ff5ec75b8d1c57c716e32e401c799c8f7e20107391

Tx prefix hash: dc31d4b81ddc7213603eeb61171e9b8ff28ce4cc3ac6d016ba2bcba290955dda
Tx public key: c085d5f3f8ff706e7893ffdb79dc0ad0a56c7577fc97ae5bdd24bc42730b7045
Timestamp: 1744194059 Timestamp [UCT]: 2025-04-09 10:20:59 Age [y:d:h:m:s]: 00:035:19:48:43
Block: 1257638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25631 RingCT/type: yes/0
Extra: 01c085d5f3f8ff706e7893ffdb79dc0ad0a56c7577fc97ae5bdd24bc42730b70450211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec682a5419fd1d4968c88a89e96caf277b8d80a764328258c5b1114f0cd8ff2f 0.600000000000 1744765 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": 1257648, "vin": [ { "gen": { "height": 1257638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec682a5419fd1d4968c88a89e96caf277b8d80a764328258c5b1114f0cd8ff2f" } } ], "extra": [ 1, 192, 133, 213, 243, 248, 255, 112, 110, 120, 147, 255, 219, 121, 220, 10, 208, 165, 108, 117, 119, 252, 151, 174, 91, 221, 36, 188, 66, 115, 11, 112, 69, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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