Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0374735eb62471249b3eccf5db8a5bf3ff409a21cc15e73fb8f6771a01d52c4e

Tx prefix hash: 007243b698f53fd9187566864e421768746632af531b0a8b8f62beadb61cfaf4
Tx public key: 0fab260dfb799566db373ff350ca0ce3c1a9fd8de053efbb794f50019c8c74b6
Timestamp: 1744292109 Timestamp [UTC]: 2025-04-10 13:35:09 Age [y:d:h:m:s]: 01:215:08:31:02
Block: 1258451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417714 RingCT/type: yes/0
Extra: 010fab260dfb799566db373ff350ca0ce3c1a9fd8de053efbb794f50019c8c74b6021100000003dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3acc562160b2f11007a45649ec06519ebe98e4a82b3b00d51156e9fdcd40f5f1 0.000600000000 1745584 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": 1258461, "vin": [ { "gen": { "height": 1258451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3acc562160b2f11007a45649ec06519ebe98e4a82b3b00d51156e9fdcd40f5f1" } } ], "extra": [ 1, 15, 171, 38, 13, 251, 121, 149, 102, 219, 55, 63, 243, 80, 202, 12, 227, 193, 169, 253, 141, 224, 83, 239, 187, 121, 79, 80, 1, 156, 140, 116, 182, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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: