Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5e250bef3491dffc644793d2e5bb5d6a1e17e20f3e44bce2e838d85f714e2a2

Tx prefix hash: f74f2e3302bb41ecba7840625f25a81f4f426880f4f5299b37ab3883b759c9e1
Tx public key: 193273ce71c2a6a175dcaadc2fb22d6d183094c46705cfffd12142591bdf34f3
Timestamp: 1741402742 Timestamp [UTC]: 2025-03-08 02:59:02 Age [y:d:h:m:s]: 01:252:22:33:04
Block: 1234532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444771 RingCT/type: yes/0
Extra: 01193273ce71c2a6a175dcaadc2fb22d6d183094c46705cfffd12142591bdf34f302110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e3b7fd4a8fb27391d42529f54bdf1dc106cdb2d0ec1e3e38ee3cf8001b688b3a 0.000600000000 1721461 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": 1234542, "vin": [ { "gen": { "height": 1234532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3b7fd4a8fb27391d42529f54bdf1dc106cdb2d0ec1e3e38ee3cf8001b688b3a" } } ], "extra": [ 1, 25, 50, 115, 206, 113, 194, 166, 161, 117, 220, 170, 220, 47, 178, 45, 109, 24, 48, 148, 196, 103, 5, 207, 255, 209, 33, 66, 89, 27, 223, 52, 243, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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: