Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99fd1506f891e8cc296dfb8241f0ba022e487058f9f8f738ce2daa5d3e0ffa5a

Tx prefix hash: 0167c05a006c5dfd5cb71768e1bde3f1f07fc2b18bd41aec2c11a7b20489378c
Tx public key: 25c3fd150ee6a419f9d4a68e1a4420026bdc84d5c4f95ebf26d8e29d2ea34524
Timestamp: 1742135320 Timestamp [UTC]: 2025-03-16 14:28:40 Age [y:d:h:m:s]: 01:249:00:19:57
Block: 1240623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442139 RingCT/type: yes/0
Extra: 0125c3fd150ee6a419f9d4a68e1a4420026bdc84d5c4f95ebf26d8e29d2ea345240211000000091f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: eb474ec82bf6a5bba5fac9fad1b351ef1cade6d360cc91279ebad21e2cd85d3c 0.000600000000 1727596 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": 1240633, "vin": [ { "gen": { "height": 1240623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb474ec82bf6a5bba5fac9fad1b351ef1cade6d360cc91279ebad21e2cd85d3c" } } ], "extra": [ 1, 37, 195, 253, 21, 14, 230, 164, 25, 249, 212, 166, 142, 26, 68, 32, 2, 107, 220, 132, 213, 196, 249, 94, 191, 38, 216, 226, 157, 46, 163, 69, 36, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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: