Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559a1db423570c3785746d9b5be0ab29f37a88b9c2d2dc5328540662adf89e5a

Tx prefix hash: bb51be55a8ed6bb1e69520053a8c1ffd4a7b75b0e1f92706eaae46c84fe04bb8
Tx public key: 8c45af83ab1bffd0fab7d4fec40e87f9860228267f424b72f1a948728b13baa3
Timestamp: 1737718929 Timestamp [UCT]: 2025-01-24 11:42:09 Age [y:d:h:m:s]: 00:144:05:02:14
Block: 1204259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102813 RingCT/type: yes/0
Extra: 018c45af83ab1bffd0fab7d4fec40e87f9860228267f424b72f1a948728b13baa30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5e6ddbc08b5f6c828548aecb4cc0ea30a43b71d9b6a33505fe9f653f4d857dd 0.600000000000 1690944 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": 1204269, "vin": [ { "gen": { "height": 1204259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5e6ddbc08b5f6c828548aecb4cc0ea30a43b71d9b6a33505fe9f653f4d857dd" } } ], "extra": [ 1, 140, 69, 175, 131, 171, 27, 255, 208, 250, 183, 212, 254, 196, 14, 135, 249, 134, 2, 40, 38, 127, 66, 75, 114, 241, 169, 72, 114, 139, 19, 186, 163, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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