Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5983780c682d4ae8b1175ada0cd72d3c5d2f4af7ede4aa40c34a8c42140e9c00

Tx prefix hash: 50c7e229d45cb38293eb2c89a71c5c961905e043d66f12c59d030d30f8ddb1bb
Tx public key: c0dcf2ea4701d24d05821800240d1c220ddd812761ba9c20e187b99b890687b5
Timestamp: 1751841228 Timestamp [UCT]: 2025-07-06 22:33:48 Age [y:d:h:m:s]: 00:130:09:11:17
Block: 1320214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91595 RingCT/type: yes/0
Extra: 01c0dcf2ea4701d24d05821800240d1c220ddd812761ba9c20e187b99b890687b5021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdf05f0261525db712c7b0d786ac63ef0ec65e1199a8eb8fe98b191da880d58f 0.600000000000 1807911 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": 1320224, "vin": [ { "gen": { "height": 1320214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdf05f0261525db712c7b0d786ac63ef0ec65e1199a8eb8fe98b191da880d58f" } } ], "extra": [ 1, 192, 220, 242, 234, 71, 1, 210, 77, 5, 130, 24, 0, 36, 13, 28, 34, 13, 221, 129, 39, 97, 186, 156, 32, 225, 135, 185, 155, 137, 6, 135, 181, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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