Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee67ad65039917daa26b8bfe8a96289b9eb0d71cf54bb3750718bb5fcf7198e5

Tx prefix hash: 0fb8ab6f1120f775ed7b23ea728af02a09a3bc9cd2c87d7c379c4869c86b9414
Tx public key: 542050c7d89bb45907a714c10710812a6de603b29fc8a998bbe5dfb2a87e93ed
Timestamp: 1742568926 Timestamp [UTC]: 2025-03-21 14:55:26 Age [y:d:h:m:s]: 01:243:22:49:53
Block: 1244185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438548 RingCT/type: yes/0
Extra: 01542050c7d89bb45907a714c10710812a6de603b29fc8a998bbe5dfb2a87e93ed0211000000018e29e1b8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ddf2a10e45346ac65d064b940a301cbe543bd877700e1d1557bb5324bf6f27ad 0.000600000000 1731176 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": 1244195, "vin": [ { "gen": { "height": 1244185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf2a10e45346ac65d064b940a301cbe543bd877700e1d1557bb5324bf6f27ad" } } ], "extra": [ 1, 84, 32, 80, 199, 216, 155, 180, 89, 7, 167, 20, 193, 7, 16, 129, 42, 109, 230, 3, 178, 159, 200, 169, 152, 187, 229, 223, 178, 168, 126, 147, 237, 2, 17, 0, 0, 0, 1, 142, 41, 225, 184, 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: