Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c655f0eb58368849b2ccc7315fe33339f3727322f55870291f9bf8dd207f4fd8

Tx prefix hash: fd26b4bc553355530bbff606c22df8d69a0e1be98e6f2514a80ccd7d5a1c7492
Tx public key: 9bfdbd8c3365efe41a110df05580f76be6c4f769f38e34dba76bdb82273c966a
Timestamp: 1743589519 Timestamp [UCT]: 2025-04-02 10:25:19 Age [y:d:h:m:s]: 00:230:04:47:54
Block: 1252629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162261 RingCT/type: yes/0
Extra: 019bfdbd8c3365efe41a110df05580f76be6c4f769f38e34dba76bdb82273c966a0211000000074060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6171ad65400cbc9b4d0ba88c87e007e7a3a7aa805e23b956e0ca5e60df44a871 0.600000000000 1739710 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": 1252639, "vin": [ { "gen": { "height": 1252629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6171ad65400cbc9b4d0ba88c87e007e7a3a7aa805e23b956e0ca5e60df44a871" } } ], "extra": [ 1, 155, 253, 189, 140, 51, 101, 239, 228, 26, 17, 13, 240, 85, 128, 247, 107, 230, 196, 247, 105, 243, 142, 52, 219, 167, 107, 219, 130, 39, 60, 150, 106, 2, 17, 0, 0, 0, 7, 64, 96, 246, 210, 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