Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713be10c466c1ffadf11bfb9b2ed4b59ee91cdd32c85ec6ed19e30cf432bc4e3

Tx prefix hash: 312920c50c46b5c03b1f9efbf544740e286c19b77989532adff882fa24ed385e
Tx public key: 44dd6182e2caf7f6548eea2d2d6557ca9764718cba9c8a19c5e5a1e85ea6d935
Timestamp: 1737655362 Timestamp [UCT]: 2025-01-23 18:02:42 Age [y:d:h:m:s]: 00:149:08:17:02
Block: 1203726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106426 RingCT/type: yes/0
Extra: 0144dd6182e2caf7f6548eea2d2d6557ca9764718cba9c8a19c5e5a1e85ea6d9350211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1937947bf0b09e875ce8cec34cf01789d1cdac5014e2d99c8b101566b69b129d 0.600000000000 1690405 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": 1203736, "vin": [ { "gen": { "height": 1203726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1937947bf0b09e875ce8cec34cf01789d1cdac5014e2d99c8b101566b69b129d" } } ], "extra": [ 1, 68, 221, 97, 130, 226, 202, 247, 246, 84, 142, 234, 45, 45, 101, 87, 202, 151, 100, 113, 140, 186, 156, 138, 25, 197, 229, 161, 232, 94, 166, 217, 53, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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