Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e3f1f084ddbf10f0df735c3cec83e426dcbe2f41fdb34c426ffe5891e08b141

Tx prefix hash: b4f2a48e3680e31a3d30a6feb4cb3e28b2e92ec2c57c2f1745b154a505769e11
Tx public key: 1207ebb02bb8dd6fa7950d374dd059dc28d8f4a13a492b850196b9e8c880e2d2
Timestamp: 1773993028 Timestamp [UTC]: 2026-03-20 07:50:28 Age [y:d:h:m:s]: 00:240:00:49:21
Block: 1501764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177011 RingCT/type: yes/0
Extra: 011207ebb02bb8dd6fa7950d374dd059dc28d8f4a13a492b850196b9e8c880e2d2021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d914a77271fd4d8a47e7a55e162e526d15ba9e4dbd0fedf7ff1322ce1860ebd6 0.000600000000 1991450 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": 1501774, "vin": [ { "gen": { "height": 1501764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d914a77271fd4d8a47e7a55e162e526d15ba9e4dbd0fedf7ff1322ce1860ebd6" } } ], "extra": [ 1, 18, 7, 235, 176, 43, 184, 221, 111, 167, 149, 13, 55, 77, 208, 89, 220, 40, 216, 244, 161, 58, 73, 43, 133, 1, 150, 185, 232, 200, 128, 226, 210, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: