Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 937bde2fd3656d88e698b071a96b92c7dd3e2eea9fe274c7bd40e6313a6afe7c

Tx prefix hash: cbe68430b59629cda6a8194cf89f95b13a01f53cbda2bee4404a3a44494a82e1
Tx public key: dc79759a70936d79a948451704345138631756a07e0ce54e860b851b066eece9
Timestamp: 1763377553 Timestamp [UCT]: 2025-11-17 11:05:53 Age [y:d:h:m:s]: 00:047:00:33:23
Block: 1414047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33680 RingCT/type: yes/0
Extra: 01dc79759a70936d79a948451704345138631756a07e0ce54e860b851b066eece9021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d512d669f7b9f07a757b7f91a990f9f940337fadedd5df673210f4e452244384 0.600000000000 1902532 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": 1414057, "vin": [ { "gen": { "height": 1414047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d512d669f7b9f07a757b7f91a990f9f940337fadedd5df673210f4e452244384" } } ], "extra": [ 1, 220, 121, 117, 154, 112, 147, 109, 121, 169, 72, 69, 23, 4, 52, 81, 56, 99, 23, 86, 160, 126, 12, 229, 78, 134, 11, 133, 27, 6, 110, 236, 233, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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