Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad82947c76b96641e5daaa079c9dfc2937dfd786e0c460ebd37df6af0ef84ab2

Tx prefix hash: 00c2d83a210e49ba07a96e125f9d1b4c0085409dd59bcef4478eca038415ff3b
Tx public key: 25c34fa80ab6417ca639a5e7517f0aa45483ef6cbf331fe88f61dc77fdea3064
Timestamp: 1772460483 Timestamp [UTC]: 2026-03-02 14:08:03 Age [y:d:h:m:s]: 00:263:15:37:56
Block: 1489111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194093 RingCT/type: yes/0
Extra: 0125c34fa80ab6417ca639a5e7517f0aa45483ef6cbf331fe88f61dc77fdea3064021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 251899be06ab520ef57dfb20cc5d309950955f564d2977c9ae3ee7c96d57f95c 0.000600000000 1978599 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": 1489121, "vin": [ { "gen": { "height": 1489111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "251899be06ab520ef57dfb20cc5d309950955f564d2977c9ae3ee7c96d57f95c" } } ], "extra": [ 1, 37, 195, 79, 168, 10, 182, 65, 124, 166, 57, 165, 231, 81, 127, 10, 164, 84, 131, 239, 108, 191, 51, 31, 232, 143, 97, 220, 119, 253, 234, 48, 100, 2, 17, 0, 0, 0, 3, 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: