Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ead57762a8bf5a7f67db1ac2af77409ed01e71e1afe80d844e768f5cf2cfcd1

Tx prefix hash: 819de6e1f394a413e13305a5693e9594a1855f7f1b8a7d5d541c4f69690a45a3
Tx public key: fb6bb68eaf221d82b6703088b6966083ac6a5df17b67eadd7375dc06312de44c
Timestamp: 1756961139 Timestamp [UTC]: 2025-09-04 04:45:39 Age [y:d:h:m:s]: 01:077:04:10:39
Block: 1360940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321617 RingCT/type: yes/0
Extra: 01fb6bb68eaf221d82b6703088b6966083ac6a5df17b67eadd7375dc06312de44c021100000004ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 572e248f8ddfb1df6aeba1f726433f9ec4e87f595f8106e80fc28299eb39e313 0.000600000000 1848953 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": 1360950, "vin": [ { "gen": { "height": 1360940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "572e248f8ddfb1df6aeba1f726433f9ec4e87f595f8106e80fc28299eb39e313" } } ], "extra": [ 1, 251, 107, 182, 142, 175, 34, 29, 130, 182, 112, 48, 136, 182, 150, 96, 131, 172, 106, 93, 241, 123, 103, 234, 221, 115, 117, 220, 6, 49, 45, 228, 76, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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: