Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e2fbc82e2941e701ebb60a42765b66b73c70fb66db713ce34c3ebf1a448976d

Tx prefix hash: 3461a4268ee0315cef28f3f5dfb0a4be70dbfb6eee0c9561a76ff82fbc9ffced
Tx public key: 36126458d85bcc198ee930b3d07c15d04fb7ecddcbff6ba38fa17a3a3911a1bc
Timestamp: 1773932933 Timestamp [UTC]: 2026-03-19 15:08:53 Age [y:d:h:m:s]: 00:240:13:19:00
Block: 1501285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177352 RingCT/type: yes/0
Extra: 0136126458d85bcc198ee930b3d07c15d04fb7ecddcbff6ba38fa17a3a3911a1bc021100000012f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a73e3e3eca234675810f0bb781c97a16bf39c76e69808846c6022693a4e773b0 0.000600000000 1990969 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": 1501295, "vin": [ { "gen": { "height": 1501285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a73e3e3eca234675810f0bb781c97a16bf39c76e69808846c6022693a4e773b0" } } ], "extra": [ 1, 54, 18, 100, 88, 216, 91, 204, 25, 142, 233, 48, 179, 208, 124, 21, 208, 79, 183, 236, 221, 203, 255, 107, 163, 143, 161, 122, 58, 57, 17, 161, 188, 2, 17, 0, 0, 0, 18, 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: