Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb62ff7a145392c07c8ce6914b2d87b0658d1df1509769cc62ce0d6f7e8a9bc

Tx prefix hash: af6ebb5fa504c7b1fa01b60f5bee64715d30569b312d1cf1c1fb7b6a5cd0c204
Tx public key: 406d12a9df45eafb9b01a933e23d16b7b2f1026fe4005fda78a386f560824940
Timestamp: 1774868614 Timestamp [UTC]: 2026-03-30 11:03:34 Age [y:d:h:m:s]: 00:233:14:18:58
Block: 1509037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172496 RingCT/type: yes/0
Extra: 01406d12a9df45eafb9b01a933e23d16b7b2f1026fe4005fda78a386f560824940021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6d15fa15ff6c98743a3b3d9a56a75b6fe6841b00b4a7d75638222d094b327e54 0.000600000000 1998791 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": 1509047, "vin": [ { "gen": { "height": 1509037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d15fa15ff6c98743a3b3d9a56a75b6fe6841b00b4a7d75638222d094b327e54" } } ], "extra": [ 1, 64, 109, 18, 169, 223, 69, 234, 251, 155, 1, 169, 51, 226, 61, 22, 183, 178, 241, 2, 111, 228, 0, 95, 218, 120, 163, 134, 245, 96, 130, 73, 64, 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: