Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb5eefc42462ad3117e5903343fa1f5b95f1e1d0c834792ea20ca47f5b6fbd8

Tx prefix hash: ee5621a655c13706751438a67d954bea6e42da1adb864c558de1f253dc19f69c
Tx public key: d12b89a938821bd51f7a479a8fe2a57737c227c6ea7e7950f800c97001087a22
Timestamp: 1707066512 Timestamp [UCT]: 2024-02-04 17:08:32 Age [y:d:h:m:s]: 00:284:20:21:43
Block: 950316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203954 RingCT/type: yes/0
Extra: 01d12b89a938821bd51f7a479a8fe2a57737c227c6ea7e7950f800c97001087a2202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e28a861e90979fba6cfb9ceb3185e1a56bd6b39b22070fe0101b8f3041f3cbe8 0.600000000000 1408914 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": 950326, "vin": [ { "gen": { "height": 950316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e28a861e90979fba6cfb9ceb3185e1a56bd6b39b22070fe0101b8f3041f3cbe8" } } ], "extra": [ 1, 209, 43, 137, 169, 56, 130, 27, 213, 31, 122, 71, 154, 143, 226, 165, 119, 55, 194, 39, 198, 234, 126, 121, 80, 248, 0, 201, 112, 1, 8, 122, 34, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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