Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72a6b8f82db7c97bae2c584814ee2aa124139840f53db9966fca70e6f479df68

Tx prefix hash: b211d0e059ead0e1bf4e1943957740af4862ac79c7d879f11924841e7a9b2d13
Tx public key: 638a2d1f2ee2f7ee3ff8596c0e8521cdef1d3438435bfa5df43d1adb0ae0ec42
Timestamp: 1772830930 Timestamp [UTC]: 2026-03-06 21:02:10 Age [y:d:h:m:s]: 00:256:06:03:17
Block: 1492190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188643 RingCT/type: yes/0
Extra: 01638a2d1f2ee2f7ee3ff8596c0e8521cdef1d3438435bfa5df43d1adb0ae0ec42021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 33482c160e5e93aebb3b14d14faaa825d1e0771f38b395885785f99521ee3d4e 0.000600000000 1981728 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": 1492200, "vin": [ { "gen": { "height": 1492190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33482c160e5e93aebb3b14d14faaa825d1e0771f38b395885785f99521ee3d4e" } } ], "extra": [ 1, 99, 138, 45, 31, 46, 226, 247, 238, 63, 248, 89, 108, 14, 133, 33, 205, 239, 29, 52, 56, 67, 91, 250, 93, 244, 61, 26, 219, 10, 224, 236, 66, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: