Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ce5993fcba288757014c283a52365b7c9d271dc38646c0f7359e476e22c138d

Tx prefix hash: 777cf9934777d193bfea0a2f8de7fc6ed5a0e9d6f3def97815935b20afcd6ca1
Tx public key: a9bd971ed7ae8379ef20a922fecb1f0c6de67c401e9371324564b52ce97a45f0
Timestamp: 1749797140 Timestamp [UCT]: 2025-06-13 06:45:40 Age [y:d:h:m:s]: 00:159:17:43:43
Block: 1303973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111910 RingCT/type: yes/0
Extra: 01a9bd971ed7ae8379ef20a922fecb1f0c6de67c401e9371324564b52ce97a45f0021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f31c99aa89678cc4ec1ed80738b998bc821eced5c2141c97d8f736229eb516d 0.600000000000 1791558 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": 1303983, "vin": [ { "gen": { "height": 1303973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f31c99aa89678cc4ec1ed80738b998bc821eced5c2141c97d8f736229eb516d" } } ], "extra": [ 1, 169, 189, 151, 30, 215, 174, 131, 121, 239, 32, 169, 34, 254, 203, 31, 12, 109, 230, 124, 64, 30, 147, 113, 50, 69, 100, 181, 44, 233, 122, 69, 240, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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