Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b732eddaff998787b9bf72130cfb9c4e843c4145c554bacfe4bd6cfb328577a7

Tx prefix hash: a9a36135a83bae0cce7b651363d1ff43f6aecdd0516f8f1d2aa817e87708b93d
Tx public key: 4aa3bc4da8dbf9505226311de48892e71b1132ccdb6d1340ed377b848b8c935a
Timestamp: 1747576770 Timestamp [UTC]: 2025-05-18 13:59:30 Age [y:d:h:m:s]: 01:187:15:36:22
Block: 1285641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397853 RingCT/type: yes/0
Extra: 014aa3bc4da8dbf9505226311de48892e71b1132ccdb6d1340ed377b848b8c935a0211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3e980f3edc6e20c8cc88330c26a7d26aaf1e0628fa81f8890351ac176e190a1e 0.000600000000 1773106 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": 1285651, "vin": [ { "gen": { "height": 1285641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e980f3edc6e20c8cc88330c26a7d26aaf1e0628fa81f8890351ac176e190a1e" } } ], "extra": [ 1, 74, 163, 188, 77, 168, 219, 249, 80, 82, 38, 49, 29, 228, 136, 146, 231, 27, 17, 50, 204, 219, 109, 19, 64, 237, 55, 123, 132, 139, 140, 147, 90, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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