Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1daa93a893672c77c8b76e6d06f3a01b8d36e9689c2bb0f82cc3e398ff6cd386

Tx prefix hash: 5f7d2bccfc833be6ff4596ce29e354ea02b050d056dc35180e62008adfc40c02
Tx public key: 8b8489e89674d6734d24babce0e3c4918a1a84fe1b818e4a03de2127eef80bac
Timestamp: 1770156815 Timestamp [UTC]: 2026-02-03 22:13:35 Age [y:d:h:m:s]: 00:012:12:45:48
Block: 1470075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 8923 RingCT/type: yes/0
Extra: 018b8489e89674d6734d24babce0e3c4918a1a84fe1b818e4a03de2127eef80bac02088782910b0057062c

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aff19a1e162b5aa37ca69eaae29ddd7502826a767058ecf5c3d80959ba2b0eba 0.000600000000 1959343 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 dinastycoin-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": 1470085, "vin": [ { "gen": { "height": 1470075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aff19a1e162b5aa37ca69eaae29ddd7502826a767058ecf5c3d80959ba2b0eba" } } ], "extra": [ 1, 139, 132, 137, 232, 150, 116, 214, 115, 77, 36, 186, 188, 224, 227, 196, 145, 138, 26, 132, 254, 27, 129, 142, 74, 3, 222, 33, 39, 238, 248, 11, 172, 2, 8, 135, 130, 145, 11, 0, 87, 6, 44 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369