Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565525c329e6cf138fd6d1a2d62dc5e8e10a86570e61ee6e55bdf97076a1fc5c

Tx prefix hash: bf79f028d9009e27dc45c8e03c5fc175a5ce89b78e27adaa50236d43cb7ba55e
Tx public key: 4ac4237325d1ffa006ac9898d4208d71a414c5d3876f9694f40112aa02a3a1f3
Timestamp: 1737489568 Timestamp [UTC]: 2025-01-21 19:59:28 Age [y:d:h:m:s]: 01:301:06:21:51
Block: 1202353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479205 RingCT/type: yes/0
Extra: 014ac4237325d1ffa006ac9898d4208d71a414c5d3876f9694f40112aa02a3a1f3021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 125b4aaff207fdead616e9ae84fc29ac84c87c0a0dbc710f9dfba5bf4261c067 0.000600000000 1689016 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": 1202363, "vin": [ { "gen": { "height": 1202353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "125b4aaff207fdead616e9ae84fc29ac84c87c0a0dbc710f9dfba5bf4261c067" } } ], "extra": [ 1, 74, 196, 35, 115, 37, 209, 255, 160, 6, 172, 152, 152, 212, 32, 141, 113, 164, 20, 197, 211, 135, 111, 150, 148, 244, 1, 18, 170, 2, 163, 161, 243, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: