Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ef3daa2b83c087ae3a457d6b1cc12824738fbc2fd3790191c3f65e1d45e672f

Tx prefix hash: ebfbf4af8af4c581481126d8a00b02dd0ad79a4c15809924ec2dad696d9569c6
Tx public key: 01758f77db9914bb8c12db73a3da1594642663157ec591a6112f2bb3f80f7f0b
Timestamp: 1774018375 Timestamp [UTC]: 2026-03-20 14:52:55 Age [y:d:h:m:s]: 00:239:20:23:10
Block: 1501979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176875 RingCT/type: yes/0
Extra: 0101758f77db9914bb8c12db73a3da1594642663157ec591a6112f2bb3f80f7f0b021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05019b724fa48f2b491d7bbb6550d6b81749e7eb10b742fdc99a23e0defaedf0 0.000600000000 1991673 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": 1501989, "vin": [ { "gen": { "height": 1501979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05019b724fa48f2b491d7bbb6550d6b81749e7eb10b742fdc99a23e0defaedf0" } } ], "extra": [ 1, 1, 117, 143, 119, 219, 153, 20, 187, 140, 18, 219, 115, 163, 218, 21, 148, 100, 38, 99, 21, 126, 197, 145, 166, 17, 47, 43, 179, 248, 15, 127, 11, 2, 17, 0, 0, 0, 5, 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: