Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d533bb3703fc599eab7bfea7fafa145f3525fa18baf3bb87c5958ee2101975d5

Tx prefix hash: df693f2c010b6f852948992d5e16ceb6e91eb3fcc462bb5d7d472a887eb5e9b4
Tx public key: d60d1a5f7c2233e87338e947b2784e869367d8d21a7c23c1c6806a76852d4286
Timestamp: 1734020252 Timestamp [UCT]: 2024-12-12 16:17:32 Age [y:d:h:m:s]: 00:093:01:56:00
Block: 1173700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66313 RingCT/type: yes/0
Extra: 01d60d1a5f7c2233e87338e947b2784e869367d8d21a7c23c1c6806a76852d4286021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e62507c9009883da322ccd663b7a0336d3e681e8cef70602530605d37b6cb490 0.600000000000 1659751 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": 1173710, "vin": [ { "gen": { "height": 1173700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e62507c9009883da322ccd663b7a0336d3e681e8cef70602530605d37b6cb490" } } ], "extra": [ 1, 214, 13, 26, 95, 124, 34, 51, 232, 115, 56, 233, 71, 178, 120, 78, 134, 147, 103, 216, 210, 26, 124, 35, 193, 198, 128, 106, 118, 133, 45, 66, 134, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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