Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bbb414a0f393b930cb9bf2639c8732b197afbd4a8140c84bd5670c2632828b9

Tx prefix hash: ef427cf6218822c18b188d26f243f047dd30c1a562d80d8a1d78f17ce256bc2f
Tx public key: 3d6deefce5d050d4dbd5dc70ad170f0068134731d2ac6b1b12935b0d2b95fd61
Timestamp: 1755189413 Timestamp [UCT]: 2025-08-14 16:36:53 Age [y:d:h:m:s]: 00:052:08:40:25
Block: 1346765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36910 RingCT/type: yes/0
Extra: 013d6deefce5d050d4dbd5dc70ad170f0068134731d2ac6b1b12935b0d2b95fd610211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7b370413b5b65bc50f12c5950896698501eb391acae97cbccdce88f2e242dcf 0.600000000000 1834670 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": 1346775, "vin": [ { "gen": { "height": 1346765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7b370413b5b65bc50f12c5950896698501eb391acae97cbccdce88f2e242dcf" } } ], "extra": [ 1, 61, 109, 238, 252, 229, 208, 80, 212, 219, 213, 220, 112, 173, 23, 15, 0, 104, 19, 71, 49, 210, 172, 107, 27, 18, 147, 91, 13, 43, 149, 253, 97, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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