Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5310eda580835bac223812c2aec0cb88ab0c615378bd8bf95e7fa4d6b6fb8545

Tx prefix hash: 02858f88873a402d234690cabd7dc6861bdb41520c61333487031625e8a874ae
Tx public key: e7f00004f33919d87eeead33b2a77226d80d3f1360f7a3aaa8ab755e5036598f
Timestamp: 1742044825 Timestamp [UTC]: 2025-03-15 13:20:25 Age [y:d:h:m:s]: 01:250:21:22:37
Block: 1239863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443496 RingCT/type: yes/0
Extra: 01e7f00004f33919d87eeead33b2a77226d80d3f1360f7a3aaa8ab755e5036598f021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b82823f6e5903c846a8b154cbaae1d7a3b08fa927a4154d135c1bcabe1de0de4 0.000600000000 1726828 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": 1239873, "vin": [ { "gen": { "height": 1239863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b82823f6e5903c846a8b154cbaae1d7a3b08fa927a4154d135c1bcabe1de0de4" } } ], "extra": [ 1, 231, 240, 0, 4, 243, 57, 25, 216, 126, 238, 173, 51, 178, 167, 114, 38, 216, 13, 63, 19, 96, 247, 163, 170, 168, 171, 117, 94, 80, 54, 89, 143, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: