Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a656f7f12ecdff869d2e9971e50e2f7606d8e64348f38bd4fce28767f4d9e5f3

Tx prefix hash: ad71071facbe2369ff722ea1525e8eb2a78334ee7f447d6a2ff7908aa89862b4
Tx public key: 50093782e3c771dc7584d024930362091925cb43d2f653ebe47fe3aadb33bf0d
Timestamp: 1744112361 Timestamp [UTC]: 2025-04-08 11:39:21 Age [y:d:h:m:s]: 01:128:16:54:48
Block: 1256954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356633 RingCT/type: yes/0
Extra: 0150093782e3c771dc7584d024930362091925cb43d2f653ebe47fe3aadb33bf0d021100000006dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ee15f281c1837fe7e3da0618c19b64f494f34a1c30ac0a16193983efe2e469d8 0.000600000000 1744073 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": 1256964, "vin": [ { "gen": { "height": 1256954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee15f281c1837fe7e3da0618c19b64f494f34a1c30ac0a16193983efe2e469d8" } } ], "extra": [ 1, 80, 9, 55, 130, 227, 199, 113, 220, 117, 132, 208, 36, 147, 3, 98, 9, 25, 37, 203, 67, 210, 246, 83, 235, 228, 127, 227, 170, 219, 51, 191, 13, 2, 17, 0, 0, 0, 6, 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: