Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dedf63a5ba1b3f5734ffe2848f049049b4e4a7ee8b08f5239a3d1de1f6e8edf

Tx prefix hash: b5f7ce7cf2dad0ea69d27695588a7aca605e590abc72ebc33978375e95781fb0
Tx public key: 34b687d1b79cbfd2f275ec58f3ef8cd12f7e1d270e25db1ea4460aafe49a376a
Timestamp: 1773852642 Timestamp [UTC]: 2026-03-18 16:50:42 Age [y:d:h:m:s]: 00:243:00:08:53
Block: 1500608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179172 RingCT/type: yes/0
Extra: 0134b687d1b79cbfd2f275ec58f3ef8cd12f7e1d270e25db1ea4460aafe49a376a021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a79c4cb064bdeb7f8b175de8db394aeb42d4bcb52fef6b98c10448a12da6f714 0.000600000000 1990282 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": 1500618, "vin": [ { "gen": { "height": 1500608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a79c4cb064bdeb7f8b175de8db394aeb42d4bcb52fef6b98c10448a12da6f714" } } ], "extra": [ 1, 52, 182, 135, 209, 183, 156, 191, 210, 242, 117, 236, 88, 243, 239, 140, 209, 47, 126, 29, 39, 14, 37, 219, 30, 164, 70, 10, 175, 228, 154, 55, 106, 2, 17, 0, 0, 0, 8, 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: