Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eb584a335f4089e4be131daee711125bc22dc44014e50ede8b0f17c57e0fea2

Tx prefix hash: 753a5e9b6d8b640c31ca06c959335cba77b8f79c91547ef82b89eb2ee528d832
Tx public key: c0c02612e6595eda99b8125841eba71f8a9f613d27b22b26d891096fc88bfba7
Timestamp: 1765226796 Timestamp [UCT]: 2025-12-08 20:46:36 Age [y:d:h:m:s]: 00:014:18:54:30
Block: 1429379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10572 RingCT/type: yes/0
Extra: 01c0c02612e6595eda99b8125841eba71f8a9f613d27b22b26d891096fc88bfba70211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd20f568aa87066b067fc35bcfe447d84d4f8fc83db54f9ccf415bea89ec451b 0.600000000000 1918104 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": 1429389, "vin": [ { "gen": { "height": 1429379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd20f568aa87066b067fc35bcfe447d84d4f8fc83db54f9ccf415bea89ec451b" } } ], "extra": [ 1, 192, 192, 38, 18, 230, 89, 94, 218, 153, 184, 18, 88, 65, 235, 167, 31, 138, 159, 97, 61, 39, 178, 43, 38, 216, 145, 9, 111, 200, 139, 251, 167, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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