Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fe808d46ea41bc57fd0e5bc6f2ca9f24fe742ea276717e8bfa5a27097a5c853

Tx prefix hash: 4c3fa92a4918c641b4b7b7d66ee7fb94c7d74870e91b209224a66d6eac41c861
Tx public key: 9c61e5320fc0aff60c70b78949b40b80b324768f3746fde828172c87c70981e9
Timestamp: 1754770964 Timestamp [UCT]: 2025-08-09 20:22:44 Age [y:d:h:m:s]: 00:013:23:11:59
Block: 1343691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9212 RingCT/type: yes/0
Extra: 019c61e5320fc0aff60c70b78949b40b80b324768f3746fde828172c87c70981e902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 000246e9326570f1cab21ea9b30b1bea52807c2ea624c700b3d9902d0c0b5e87 0.600000000000 1831532 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 dinasty-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": 1343701, "vin": [ { "gen": { "height": 1343691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "000246e9326570f1cab21ea9b30b1bea52807c2ea624c700b3d9902d0c0b5e87" } } ], "extra": [ 1, 156, 97, 229, 50, 15, 192, 175, 246, 12, 112, 183, 137, 73, 180, 11, 128, 179, 36, 118, 143, 55, 70, 253, 232, 40, 23, 44, 135, 199, 9, 129, 233, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8