Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a077d8abd628ff52bedb513af1a54561d65ca0d6bf761ca42418bee3c9569727

Tx prefix hash: 854b4825d3141a42a6d53be84af51dcda46f92f03ef471fb4f5eaff5e57cf1c3
Tx public key: ed5e3c3610b271173402cdea73f3769760abf5b0e827885010e9094f48796110
Timestamp: 1770826274 Timestamp [UTC]: 2026-02-11 16:11:14 Age [y:d:h:m:s]: 00:276:13:48:45
Block: 1475606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203080 RingCT/type: yes/0
Extra: 01ed5e3c3610b271173402cdea73f3769760abf5b0e827885010e9094f4879611002110000000ff188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fced2feb0870fe06fe24bd06d07a7e159ba52427ad097cae103c8f83f4211c6c 0.000600000000 1964910 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": 1475616, "vin": [ { "gen": { "height": 1475606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fced2feb0870fe06fe24bd06d07a7e159ba52427ad097cae103c8f83f4211c6c" } } ], "extra": [ 1, 237, 94, 60, 54, 16, 178, 113, 23, 52, 2, 205, 234, 115, 243, 118, 151, 96, 171, 245, 176, 232, 39, 136, 80, 16, 233, 9, 79, 72, 121, 97, 16, 2, 17, 0, 0, 0, 15, 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: