Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4d2b6a5305d37f7abf71b380f4eb84fe8f4179dea81f795914cf0fcc26f3d3

Tx prefix hash: 8551a5d55ea070996e9ee11557bca4d1faaf858260ba13431609ca413fcd29cc
Tx public key: 763aa2ea8713ba363e03c5d66547165d842c2112da48c231d04c3662dc87e950
Timestamp: 1744384711 Timestamp [UTC]: 2025-04-11 15:18:31 Age [y:d:h:m:s]: 01:224:00:45:35
Block: 1259220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424274 RingCT/type: yes/0
Extra: 01763aa2ea8713ba363e03c5d66547165d842c2112da48c231d04c3662dc87e950021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a22f07497402157e19b9fa7d82b043655fcdf35c83e2a4a240e9292a7cbf6059 0.000600000000 1746359 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": 1259230, "vin": [ { "gen": { "height": 1259220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a22f07497402157e19b9fa7d82b043655fcdf35c83e2a4a240e9292a7cbf6059" } } ], "extra": [ 1, 118, 58, 162, 234, 135, 19, 186, 54, 62, 3, 197, 214, 101, 71, 22, 93, 132, 44, 33, 18, 218, 72, 194, 49, 208, 76, 54, 98, 220, 135, 233, 80, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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: