Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30245b73c2b85fcf1fc560c32b511be106a3d7392dd91fdd88f70bb0ca9a1f01

Tx prefix hash: cbd4c35f8faae505fad76c80c03e53ffd1e2db5bfb80e65074f630acfbaf87df
Tx public key: ecbbd362a052dec3124aaf6a70a67b2c8a4dbdd8605d2607c34c99796564c247
Timestamp: 1721716535 Timestamp [UCT]: 2024-07-23 06:35:35 Age [y:d:h:m:s]: 00:254:18:15:48
Block: 1071773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182006 RingCT/type: yes/0
Extra: 01ecbbd362a052dec3124aaf6a70a67b2c8a4dbdd8605d2607c34c99796564c247021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ec6f2c45dfa0f8ef9cb9511f43e1038626b39b76564c6e5fd839707e0eabaa 0.600000000000 1544128 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": 1071783, "vin": [ { "gen": { "height": 1071773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ec6f2c45dfa0f8ef9cb9511f43e1038626b39b76564c6e5fd839707e0eabaa" } } ], "extra": [ 1, 236, 187, 211, 98, 160, 82, 222, 195, 18, 74, 175, 106, 112, 166, 123, 44, 138, 77, 189, 216, 96, 93, 38, 7, 195, 76, 153, 121, 101, 100, 194, 71, 2, 17, 0, 0, 0, 4, 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