Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddd26ff6a0e6bcfa80e37a5bdd1cd0908c6510c4f71618b6d394a6edee7e33b7

Tx prefix hash: a70ecbf055a803e5b5d3a962f783d6623b0a8d9109071eebbed0e1e4934d7080
Tx public key: da56a1a120f50224b97de35fcec37173f16aec6039d60d30fc66dea4e6aff5e5
Timestamp: 1720464459 Timestamp [UCT]: 2024-07-08 18:47:39 Age [y:d:h:m:s]: 00:270:06:40:35
Block: 1061411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193098 RingCT/type: yes/0
Extra: 01da56a1a120f50224b97de35fcec37173f16aec6039d60d30fc66dea4e6aff5e5021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da162931d7172414a8d1fa56aed5af5ea41cc8768e71cf5e96e88b9370e5c003 0.600000000000 1531902 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": 1061421, "vin": [ { "gen": { "height": 1061411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da162931d7172414a8d1fa56aed5af5ea41cc8768e71cf5e96e88b9370e5c003" } } ], "extra": [ 1, 218, 86, 161, 161, 32, 245, 2, 36, 185, 125, 227, 95, 206, 195, 113, 115, 241, 106, 236, 96, 57, 214, 13, 48, 252, 102, 222, 164, 230, 175, 245, 229, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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