Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2cd5f5c4ba55786c27c49f485311f56f7be7bf0923ba3c1bd794f9aa0a9e9c

Tx prefix hash: 625519d154c52f7591bc78053b3a8ff46b1c8d18e4078f00b45eb5844d76f0b5
Tx public key: c6b2af379829550ce2cc386a293059dc93122c47c6d22cc97334dd3d453d54ac
Timestamp: 1736422834 Timestamp [UTC]: 2025-01-09 11:40:34 Age [y:d:h:m:s]: 01:128:17:17:04
Block: 1193571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342849 RingCT/type: yes/0
Extra: 01c6b2af379829550ce2cc386a293059dc93122c47c6d22cc97334dd3d453d54ac0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c80372a1ff04f185128c32d614d3ec9686507d99cbc1ce287e9f7d547c865aa0 0.000600000000 1680134 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": 1193581, "vin": [ { "gen": { "height": 1193571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c80372a1ff04f185128c32d614d3ec9686507d99cbc1ce287e9f7d547c865aa0" } } ], "extra": [ 1, 198, 178, 175, 55, 152, 41, 85, 12, 226, 204, 56, 106, 41, 48, 89, 220, 147, 18, 44, 71, 198, 210, 44, 201, 115, 52, 221, 61, 69, 61, 84, 172, 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: